Program Boundaries and Conventions
The following is the list of program boundaries and conventions:
- The program scope is one bridge at a time. The database may contain more than one bridge, and the user can select the bridge to be worked on. Multiple bridges can be shown on the Geometry tab.
- Reports are generated in html format.
- The Wingwalls defined in Bridge Parametric Layout can't be displayed in the LEAP Bridge Concrete viewer.
- In this version, Wing walls are added as a Geometric feature, 3D model only. There are no design or 2D drawing capabilities.
- The LEAP Bridge Concrete database cannot handle curved or continuous steel girders defined in Bridge Parametric Layout.
- Since Bridge Parametric Layout calculates the elevations of pier at both ends, Substructure uses these elevations to define the straight top of the cap.
- LEAP Bridge Concrete 3D viewer shows representative, not accurate positions of all reinforcement.
- The roadway cross section slope is not supported in LEAP Bridge Concrete for box superstructure 3D graphics. (i.e. The top surface is flat and does not have slope for the generated box superstructure section.)
- For a box bridge, Substructure locks the superstructure, and any change made in Bridge Parametric Layout for the box bridge superstructure is not saved in the database.
- Bridge Parametric Layout elements like Superelevation and Delta (used for a roadway definition) are not saved in the database, so they are not displayed in LEAP Bridge Concrete.
- Curved or alignment girders can be part of the bridge in Bridge Parametric Layout, but they will be stored in the database as straight girders and displayed straight in LEAP Bridge Concrete.
- Station Offset Girders have no pier references (to be placed in a specific span), so they can't be part of the bridge in Bridge Parametric Layout and they will not be displayed in LEAP Bridge Concrete.
- Station Offset Columns have no pier referenced to be located, so they are not related to the bridge and they, and all the substructure elements related to it (footing and piles), will not be displayed in LEAP Bridge Concrete.
- Station Offset Footings have no column reference to be located, so they are not related to the bridge. They (and all the substructure elements related to it [piles]) will not be displayed in LEAP Bridge Concrete.
- Strap Footings from Substructure are converted automatically into a trapezoidal footings in Bridge Parametric Layout attached to a single column.
- Substructure does not support multiple column types defined for the same pier; an error message displays and the model is not loaded.
- Round columns with variation made by Bridge Parametric Layout are not supported by Substructure; it will convert the variation column into a straight round column. This change is not saved back to the database when leaving Substructure, so LEAP Bridge Concrete will remain with the columns coming from Bridge Parametric Layout.
- Continuous girders defined in Bridge Parametric Layout can't be added to the bridge, so they will not be visible in LEAP Bridge Concrete.
- Integration of CIP RC/PT Girder superstructure analysis with end Abutments is currently not functional.
- Drawings currently only available for prestressed girder bridges.